Skip to content

Conversation

belimawr
Copy link
Contributor

What does this PR do?

This PR adds CA_TRUSTED as an empty string env var in the K8s standalone manifest, without this env var set, the Elastic Agent fails to parse the configuration with: rendering output "default" failed: no matching vars: ${env.CA_TRUSTED}. The full error:

{
  "@timestamp": "2025-10-16T13:13:41.688Z",
  "ecs.version": "1.6.0",
  "log": {
    "source": "elastic-agent"
  },
  "log.level": "error",
  "log.origin": {
    "file.line": 1372,
    "file.name": "coordinator/coordinator.go",
    "function": "github.com/elastic/elastic-agent/internal/pkg/agent/application/coordinator.(*Coordinator).processVars"
  },
  "message": "updating Coordinator variables: generating component model: rendering outputs failed: rendering output \"default\" failed: no matching vars: ${env.CA_TRUSTED}"
}

Having the env var CA_TRUSTED as an empty string fixed the problem.

Why is it important?

It fixes our example K8s standalone manifest

Checklist

  • I have read and understood the pull request guidelines of this project.
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in ./changelog/fragments using the changelog tool
  • I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Follow the examples from Run Elastic Agent Standalone on Kubernetes, but instead of downloading the manifest, use the one from this branch. Once the correct credentials are set, the Elastic Agent should successfully send data to Elasticsearch.

## Related issues

Questions to ask yourself

  • How are we going to support this in production?
  • How are we going to measure its adoption?
  • How are we going to debug this?
  • What are the metrics I should take care of?
  • ...

This commit adds CA_TRUSTED as an empty string env var in the K8s
standalone manifest, without this env var set, the Elastic Agent fails
to parse the configuration with:
`rendering output "default" failed: no matching vars: ${env.CA_TRUSTED}`
@belimawr belimawr self-assigned this Oct 16, 2025
@belimawr belimawr requested a review from a team as a code owner October 16, 2025 14:43
@belimawr belimawr added Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team skip-changelog labels Oct 16, 2025
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

Copy link
Contributor

mergify bot commented Oct 16, 2025

This pull request does not have a backport label. Could you fix it @belimawr? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@belimawr
Copy link
Contributor Author

The failing test is known to be flaky: #8486

@elasticmachine
Copy link
Collaborator

elasticmachine commented Oct 17, 2025

💔 Build Failed

Failed CI Steps

History

cc @belimawr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changelog Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants